Path: / {BASE} / versions / {id}

Return detailed information about the version whose id is passed as path argument. Returns a JSON map with the fields id, creator, date, added_triples, removed_triples. Triple will be represented in RDF/JSON format.

Path parameters:

id ([0-9]+) - the ID of the version to return

Resource Methods

Method Summary
Name	Description
`GET /{BASE}/versions/{id}`	Return detailed information about the version whose id is passed as path argument.
`DELETE /{BASE}/versions/{id}`	Remove the version with the given ID from the triple store.
`POST /{BASE}/versions/{id}`	Revert (undo) the version with the given ID.

GET /{BASE}/versions/{id}

HTTP Example:: GET /{BASE}/versions/{id}
API Example:: VersioningWebService.getVersion({'id': /* id the ID of the version to return */});
Output:: Response - a JSON map representing the version information as described above
Produces:: application/json
HTTP return codes:: 404 - in case the requested version does not exist

DELETE /{BASE}/versions/{id}

Remove the version with the given ID from the triple store. Calling this service will only remove the versioning metadata, not the triples themselves. Triples that are marked as deleted and no longer attached to a version will be cleaned up by a garbage collection process that is running periodically or can be triggered manually.

HTTP Example:: DELETE /{BASE}/versions/{id}
API Example:: VersioningWebService.deleteVersion({'id': /* id */});
Output:: Response -

POST /{BASE}/versions/{id}

Revert (undo) the version with the given ID. Calling this service will add all removed triples and remove all added triples of the old version. If versioning is active, this will create a new version as well.

HTTP Example:: POST /{BASE}/versions/{id}
API Example:: VersioningWebService.revertVersion({'id': /* id */});
Output:: Response -